Build system redirect

ABSTRACT

Embodiments may provide a makefile interposer, which enables a makefile to be used for building software for different platforms without modifying the makefile. In some embodiments, the interposer intercepts the commands run by makefile and automatically interposes the correct library files, dependencies, paths, and other information used by make to build the program for a particular platform. Additionally, calls that the invoked tools themselves make are intercepted and the interposer may redirect them to the platform-specific tools or file system locations including redirecting file descriptors. In some instances, when a tool is called that is not in the platform, the interposer may also fall back on the other system tools.

The present application claims priority to U.S. Provisional ApplicationNo. 61/033,739, filed Mar. 4, 2008, and entitled BUILD SYSTEM REDIRECT.

BACKGROUND

Embodiments of the invention relate to a software build tool. Morespecifically, embodiments of the invention relate to techniques andmechanisms to manage building of applications including redirectingcalls to selected files.

Computer systems generally run software programs which carry out thedesired functionality of users of the computer systems. The programswhich run on the computer system are generally executable program files.An executable program file is generally a binary representation ofmachine instructions specific to the processor the program is intendedto run on. An executable program file may also be a binaryrepresentation of the machine instructions for a virtual machine. It isvery difficult for programmers to understand the binary representationof machine instructions. Even if the binary representation were to betranslated to the machine instructions themselves, it would still behard for programmers to read and understand the machine instructions.With modern computing, computer programs are now written by programmersin high-level, human readable instructions. These high levelinstructions are often referred to as “source code.” Examples of suchhigh-level languages include C, C++, and JAVA.

Unfortunately, source code is often not directly executable by thecomputer system. The high-level source code is often translated into“object files” by a compiler. The compiler reads the high-level sourcecode and creates object files which contain a machine code version ofthe source code. A program called a linker creates an executable file bytaking the object files and linking them to the appropriate libraries,modules or routines need by the program. The executable file is nowcapable of being run on the computer system.

As user requirements have become more complex and varied, programs havealso become more complex and varied. While a program may be createdusing only a single source code file, it is often easier to organize thecode into separate source code files. These separate source code modulesmay each contain parts of the complete source code for the program andmay often be organized such that they are logical representations of theoverall structure of the program. Because of the separation of thecomplete source code into modules, some modules may use or “depend” onother modules. For example, a first module may require the functions,variables or objects defined in a second module, so in order to compilethe first module, one would first have to compile the second modulefirst. Such a relationship between the first module and the secondmodule is called a “dependency.” These dependencies often complicate thecompilation process as changes in one module may result in many othermodules having to be recompiled.

In order to solve problems resulting from dependencies, a “make” utilityis used to control the compiler. The make utility keeps track of thedependencies and controls the compiler to recompile not only source codemodules that were modified, but also other modules which depend on thechanged modules. The make utility is run every time changes are made toany module so that all dependent programs or modules are properlyrecompiled. A make utility requires that the source code programmer alsocompose a specialized control file, known as a “makefile”, whichcontains instructions or commands that the make function uses to controlthe compilation and linking of each of the source code modules when themake function is executed. The makefile typically includes a hierarchyof source modules that embody the dependencies found in the program. Forexample, a makefile may include a variety of elements such as a seriesof instructions containing “targets”, dependencies, and “shell commands”for updating the targets.

BRIEF DESCRIPTION OF THE DRAWINGS

Exemplary embodiments are explained in greater detail in the followingdescription and are illustrated in the drawings, in which:

FIG. 1A shows a component diagram of a computer system running anintegrated development environment;

FIG. 1B shows another component diagram of a computer system running anintegrated development environment;

FIG. 2A shows a component diagram of a makefile interposer according toa first embodiment.

FIG. 2B shows a component diagram of a makefile interposer according toa second embodiment.

FIG. 2C shows a component diagram of a makefile interposer according toa third embodiment.

FIG. 2D shows a component diagram of a makefile interposer according toa fourth embodiment.

FIG. 2E shows a component diagram of a makefile interposer according toa fifth embodiment.

FIG. 3A shows a flow diagram of an interposing process according to afirst embodiment.

FIG. 3B shows a flow diagram of an interposing process according to asecond embodiment.

FIG. 3C shows a flow diagram of an interposing process according to athird embodiment.

FIG. 3D shows a flow diagram of an interposing process according to afourth embodiment.

FIG. 4 shows a block diagram of a computing system;

FIG. 5A illustrates an example embodiment of a mobile device.

FIG. 5B illustrates an example embodiment of a configurable top-levelgraphical user interface of a mobile device.

FIG. 6 is a block diagram of an example implementation of a mobiledevice.

DETAILED DESCRIPTION

Many software programs are created using what is known as the makeutility or some other equivalent utility. In general, each project foreach platform may require its own makefile. For example, each projectmay have its own compiler, linker, libraries, file paths, options anddependencies specified in a makefile. In addition, there is generallyone makefile for each platform the project may run on. This requires alot of duplication and extra effort to build a project for otherplatforms. It often becomes difficult to track and maintain such a largenumber of make files. A small change in one makefile would requirechanging all of the makefiles for the same project on differentplatforms. Embodiments of the present disclosure can provide a morestreamlined and efficient approach to using makefiles and can allowdevelopers to use a fewer versions of a makefile for building theirprogram. In some embodiments, the same makefile may be used to buildprograms across all targeted platforms without needing to modify it inany way. The makefile remains compatible with the original project. Thiscan alleviate the need for developers to create and maintain a makefilefor every platform they wish to build the program for, or toparameterize their makefiles and have large conditional statements tocover all the different platforms.

In build systems where other types of program build or install files areused, similar needs may exist where, for example a shell script in oneUNIX environment such as a configuration or installation script may needto be ported to another UNIX environment. Other types of such build,installation and configuration specification files are known in the art.

Embodiments may now be described with reference to the accompanyingFigures, wherein like numerals refer to like elements throughout. Theterminology used in the description presented herein is not intended tobe interpreted in any limited or restrictive manner, simply because itis being utilized in conjunction with a detailed description of certainspecific embodiments. Furthermore, embodiments may include several novelfeatures, no single one of which is solely responsible for its desirableattributes or which is essential to practicing the inventions hereindescribed.

FIG. 1A shows a component diagram of a computer system 110 running anintegrated development environment 120. The computer system 110 is anexample of a computing device running a particular set of hardware 140,software and operating system 130. The integrated developmentenvironment (IDE) 120 may run within the operating system 130 and mayuse operating system 130 to interface with the hardware 140 of thecomputer system. In on embodiment, the functionality of make utility andthe makefile may reside within the IDE 120. In another embodiment, themake utility and the makefile may be separate from IDE 120. The makeutility may use libraries 150, source code 160 build tools 170, or anyother files and applications it needs to build a program according thecommands in the makefile. The libraries 150, source code 160 build tools170, or any other files and applications may be located in a memory oncomputer system 110.

FIG. 1A shows another component diagram of a computer system 110 runningan integrated development environment 120. The computer system 110 is anexample of a computing device running a particular set of hardware 140,software and operating system 130. The IDE 120 may run within theoperating system 130 and may use operating system 130 to interface withthe hardware 140 of the computer system. In on embodiment, thefunctionality of make utility and the makefile may reside within the IDE120. In another embodiment, the make utility and the makefile may beseparate from IDE 120. The make utility illustrated in FIG. 1B may uselibraries 150, source code 160 build tools 170, or any other files andapplications it needs to build a program according the commands in themakefile. The libraries 150, source code 160 build tools 170, or anyother files and applications may be located on another computer systemand are accessed via a network “cloud” 145 which may represent a localarea network (LAN), a wide area network (WAN), the Internet, or anotherconnection service.

In other embodiments, a shell program may be invoked or another programsuch as Perl may be invoked to execute an installation or configurationscript.

FIG. 2A is a component diagram of an embodiment. Makefile 210 mayinclude commands that may be used by the make utility to build a programfor a first platform. The makefile interposer 220 may process themakefile 210. Interposing can be used to redirect commands invoked bytools in a specified platform during compilation, and may fall back toother system tools if a platform-specific tool isn't found.

In some embodiments, redirect commands invoked by make to invoke toolsin a specified platform. For example, for a platform A, which has itsown compiler, assembler, and linker, a developer may pass a path toconstruct and set an environment variable, which is picked up bymakefile interposer 220. Interposer 220 may intercept the system callsthat make uses to execute build tools, such as open( ) and execve( ), aswell as other system calls. Therefore, with interposer 220, an execvecall to cc may call Platform A's cc instead of /usr/bin/cc.

In addition, calls that the invoked tools themselves make areintercepted and interposer 220 may redirect them to theplatform-specific tools or file system locations (including redirectingfile descriptors). Hence, when cc calls execve( ) or open( ) to invoke alinker, for example, interposer 220 may pick up the linker from PlatformA.

In some instances, when a tool is called that is not in the platform,interposer 220 may fall back on the other system tools. This enablesplatform developers to sparsely provide the tools, for example, that aremodified for their platform. Furthermore, system calls like access( ) ormmap( ) that take a path or file descriptor can be intercepted andchecked for a platform-relative equivalent location, falling back to theoriginal path or file descriptor if a platform-relative one is notfound.

Accordingly, without any changes to the makefile, and without themakefile or the developer knowing anything about interposing or whichtools are defined in the platform, a makefile project can now be builtfor any platform with which its source is compatible. In other words, adeveloper may not need to alter the makefiles or make a new set ofplatform-specific makefiles. Instead, a different flag on the commandline can be passed that is recognized by makefile interposer 220.

This is merely one example of the usage of interposing to supportplatform development for makefile projects. Other examples andimplementations of this interposing mechanism are also part ofembodiments of the present invention.

The above-described interposition mechanism may for example be used tointerpose system library calls made by Perl, Python or other interpretedlanguage, or a shell interpreter while executing an installation orconfiguration script in a shell language or in an interpreted languagesuch as Perl or Python. Such interposition may then redirect calls madeby the shell or script interpreter to customize the execution of theshell script or interpreted program for a particular platform and/orenvironment. In one embodiment, the makefile interpose may be used toallow shell scripts, Perl scripts or other utilities to be used onmultiple platforms. For example, a particular set of libraries may needto be built on a platform before it can be used. Generally, when thelibrary source files are obtained, there is an installer script thatwill build and install the library files. The makefile interpose mayallows the installer script to run on another platform by interposingall calls made by the installer script so that the script can run onanother platform.

Referring now back to FIG. 2A, makefile interposer 220 may check anenvironment variable 260 to determine which platform the program may bebuilt for. In this example, the environment variable 260 may specifythat the program is to be built for a second platform. The environmentvariable 260 may include a name or any information which may be used toidentify a platform. The original compiler for platform one is specifiedin makefile 210. The makefile interposer 220 may intercept the commandwhich calls the compiler, and it may interpose (i.e. change orsubstitute) the call to the compiler for the first platform 240 with acall to the compiler for the second platform 250. In one embodiment, themake file interposer 220 may run the command specified in the makefile210. Make may call the compiler for the first platform and the makefileinterposer 220 may intercept the call to the compiler for the firstplatform 240, and redirect that call to the compiler for the secondplatform 250. This interception and redirection is done when thecompiler for the first platform is called. The makefile interposer 220may intercept any access to system resources and redirect them to theappropriate location. In one embodiment, the makefile interposer mayredirect file access made by any tool. For example, when running amakefile created for platform 1 to build an application for platform 2,any attempts to access /usr/lib/libOpenGL.dylib, which is used byplatform 1, are redirected to /MacOSX/Libraries/libOpenGL.dylib which isused by platform 2. In another embodiment, the makefile interposer 220may analyze the command and then interpose the compiler for the secondplatform 250 before calling the compiler.

In one embodiment, the makefile interposer may interpose calls made byother build systems. Make is a common build system that is often used bysoftware developers. There are a variety of other build systems used bysoftware developers including but not limited to Ant, GNU Autoconf andSCons. All calls made by such build systems may be interposed by themakefile interposer. In another embodiment, interposition may be appliedto process that launches subcommands and that reads or writes files inthe file system.

In one embodiment, the makefile may use a variable to represent whichcompiler to call. The makefile interposer 220 may read the value of thevariable, analyze the interposer specification 230, and determine if thecompiler specified by the variable is appropriate for the secondplatform. If the compiler specified it not appropriate, the makefileinterposer may use the appropriate compiler for the second platformspecified in the interposer specification 230 and interpose thatcompiler on the call. If no compiler is specified for the secondplatform in the interposer specification 230, the makefile interposer220 may use a default compiler. In another embodiment, the makefile mayexplicitly call a compiler for the first platform. The makefileinterposer 220 may analyze the compiler specified, analyze theinterposer specification 230, and determine if the compiler specified isappropriate for the second platform. If the compiler specified is notappropriate, the makefile interposer may use the appropriate compilerfor the second platform specified in the interposer specification 230and interpose that compiler on the call. If no compiler is specified forthe second platform in the interposer specification 230, the makefileinterposer 220 may use a default compiler.

In one embodiment, the makefile interposer 220 may not only interposethe call to the compiler for different platforms, the makefileinterposer 220 may also interpose to the compiler for the same platformthe makefile 220 was written for. For example, the makefile may specifythat version 4.0 of the compiler be used when building the program.However, a new version of the compiler 4.1 with needed fixes may bereleased. Rather then change all the makefiles that call version 4.0 ofthe compiler, the interposer may simply intercept all of the calls tothe older 4.0 version of the compiler and interpose the newer 4.1version of the compiler onto those calls.

FIG. 2B is a component diagram of another embodiment. Makefile 210 mayinclude commands that may be used by the make utility to build a programfor a first platform. The makefile interposer 220 may process themakefile 210. It may check an environment variable 260 to determinewhich platform the program may be built for. In this example, theenvironment variable 260 may specify that the program is to be built fora second platform. The environment variable 260 may include a name orany information which may be used to identify a platform. Library files241 are specified for platform one in makefile 210. The makefileinterposer 220 may analyze the command which lists the library files241, and it may interpose (i.e. change or substitute) the library filesfor the first platform 241 with the library files for the secondplatform 251. In one embodiment, the make file interposer 220 may runthe command specified in the makefile 210. Make may call the librariesfor the first platform 241 and the makefile interposer 220 may interceptthe call to the libraries for the first platform 241, and redirect thatcall to the libraries for the second platform 251. In anotherembodiment, the makefile interposer 220 may analyze the command and theninterpose the libraries for the second platform 251 before making thecall to the libraries.

In one embodiment, the makefile may use a variable to represent whichlibraries are used. The makefile interposer 220 may read the value ofthe variable, analyze the interposer specification 230, and determine ifthe libraries specified by the variable are appropriate for the secondplatform. If the libraries specified are not appropriate, the makefileinterposer may use the appropriate libraries for the second platformspecified in the interposer specification 230 and interpose thoselibraries. If no libraries are specified for the second platform in theinterposer specification 230, the makefile interposer 220 may use adefault set of libraries. In another embodiment, the makefile mayexplicitly list the libraries for the first platform. The makefileinterposer 220 may analyze the libraries specified, analyze theinterposer specification 230, and determine if the specified librariesare appropriate for the second platform. If the libraries specified arenot appropriate, the makefile interposer may use the appropriatelibraries for the second platform specified in the interposerspecification 230 and interpose those libraries. If no libraries arespecified for the second platform in the interposer specification 230,the makefile interposer 220 may use a default set of libraries.

FIG. 2C is a component diagram of another embodiment. Makefile 210 mayinclude commands that may be used by the make utility to build a programfor a first platform. The makefile interposer 220 may process themakefile 210. It may check an environment variable 260 to determinewhich platform the program may be built for. In this example, theenvironment variable 260 may specify that the program is to be built fora second platform. The environment variable 260 may include a name orany information which may be used to identify a platform. A utilityprogram 242 used for building the program is specified for platform onein makefile 210. The makefile interposer 220 may analyze the commandwhich calls the utility program 242, and it may interpose (i.e. changeor substitute) the utility program for the first platform 242 with thelibrary files for the second platform 252. In one embodiment, the makefile interposer 220 may run the command specified in the makefile 210.Make may call the utility program for the first platform 242 and themakefile interposer 220 may intercept the call to the utility programfor the first platform 242, and redirect that call to the utilityprogram for the second platform 252. In another embodiment, the makefileinterposer 220 may analyze the command and then interpose the utilityprogram for the second platform 252 before making the call to thelibraries.

In one embodiment, the makefile may use a variable to represent theutility program to be called. The makefile interposer 220 may read thevalue of the variable, analyze the interposer specification 230, anddetermine if the utility program specified by the variable isappropriate for the second platform. If the utility program specified isnot appropriate, the makefile interposer may use the appropriate utilityprogram for the second platform specified in the interposerspecification 230 and interpose the utility program into the call. If noutility program is specified for the second platform in the interposerspecification 230, the makefile interposer 220 may use a default utilityprogram. In another embodiment, the makefile may explicitly list theutility program for the first platform. The makefile interposer 220 mayanalyze the utility program specified, analyze the interposerspecification 230, and determine if the specified utility program isappropriate for the second platform. If the specified utility programspecified is not appropriate, the makefile interposer may use theappropriate utility program for the second platform specified in theinterposer specification 230 and interpose those libraries. If noutility program is specified for the second platform in the interposerspecification 230, the makefile interposer 220 may use a default set oflibraries.

For example, a program may use an OpenGL module in order to displayvisual images correctly. This OpenGL module may need to be compiledusing a different compiler than the compiler used to build the programfor a particular platform. A makefile may have a command which compilesthe OpenGL module first, and then uses the compiled OpenGL module tobuild the final program. In one embodiment, a different OpenGL compilermay be used for each platform. The makefile interposer would interceptthe call to the OpenGL compiler and interpose the correct compiler forthe platform into the call. In another embodiment, the makefileinterposer may not only intercept a call to a particular utility programor build tool, but it may also modify the parameters that are passed tothe utility program or build tool. For example, not only may a differentOpenGL compiler be used for the OpenGL module depending on the platform,but there may be a parameter for each platform specifying whether or notto optimize the compilation of the OpenGL module. The makefileinterposer may also interpose the parameters to the utility program inaddition to the call to the utility program itself.

In one embodiment, the interposer may be used to enforce usage ofspecific utilities or parameters regardless of whether or not themakefile is being used for another platform. For example, a build filemay be written for a particular platform, but due to licensing issues,the makefile interposer may interpose a compiler for which thedevelopers have a license for, even though the makefile is still beingused for its original intended platform. This example may applyregardless of whether or not the makefile is being used for a differentplatform. In another example, the makefile interposer may be used toenforce a particular parameter for a call. Developers may want allcompiler warnings to be ignored even though the original makefilespecified otherwise.

In another embodiment, even the source code itself may be interposed.For example, a makefile may require that a file “class1.c” be compiled.The developers may now want to use “class1-fix1.c” because the newersource code file contains an essential fix. The original makefile maystill be used to build the program, and the makefile interposer maysimply interpose the newer source code file into the call to thecompiler.

In another embodiment, the makefile interposer may dynamically determinethe intended target platform for the program without using theenvironment variable. For example, the makefile may refer to a specificset of libraries which are only used for a specific platform. Themakefile interposer may recognize the use of the set of libraries andinfer that the program is intended for the specific platform which usesthose libraries.

FIG. 2D illustrates another embodiment. In this embodiment, makefile 210calls a utility tool 243 for platform 1. Utility tool 1 in turn callsutility tool 2 for the first platform. Makefile interposer 220 may checkan environment variable 260 to determine which platform the program maybe built for. In this example, the environment variable 260 may specifythat the program is to be built for a second platform. Environmentvariable 260 may include a name or any information which may be used toidentify a platform. Makefile interposer 220 may intercept the call madeby utility tool 1 to utility tool 2 for the first platform 253. It mayinterpose the call to utility tool 2 for the first platform 253 andredirect the call to utility tool 2 for the second platform 263.

FIG. 2E illustrates a fifth embodiment. Makefile 210 may includecommands that may be used by the make utility to build a program for afirst platform. The makefile interposer 220 may process the makefile210. It may check an environment variable 260 to determine whichplatform the program may be built for. In this example, the environmentvariable 260 may specify that the program is to be built for a secondplatform. The environment variable 260 may include a name or anyinformation which may be used to identify a platform. In thisembodiment, there are no library files specified for platform two ininterposer specification 230. Makefile interposer 220 will theninterpose default libraries 256 when the libraries for the firstplatform 244 are called. In this embodiment, makefile interpose 220 isable to fall back onto default applications, tools, libraries etc. if itis unable to find the information it needs in interposer specification230.

FIG. 3A is a flow diagram of an interposing process 300 according to afirst embodiment. The process starts at step 304 where the make utilitymay first open and read the makefile. It reads one command at step 308.At step 310, the make utility runs the command. Then at step 312, themakefile interposer may check the interposer specification and anenvironment variable that indicates which platform the program isintended to run on. The makefile interposer then retrieves the requiredinformation from the interposer specification. At step 316, the commandis interposed with the appropriate information for the target platform.Once the command has been interposed, the command is executed at step320. The interposer then checks if the end of the makefile has beenreached at step 324. If there are still more commands to run, theprocess then loops back to step 308. If there are no more commands torun, then process ends at step 328.

FIG. 3B is a flow diagram of an interposing process 350 according to asecond embodiment. The process starts at step 354 where the make utilitymay first open and read the makefile. The make utility then reads onecommand at step 358. At step 360, the make utility runs the command.Then at step 362, the makefile interposer may check to see if theinformation that needs to interposed has been previously accessed andbuffered. If the information that needs to be interposed has beenbuffered, the process may move onto step 374. If the information has notbeen buffered, the process then proceeds to step 366 where the makefileinterposer may check the interposer specification and an environmentvariable that indicates which platform the program is intended to runon. The makefile interposer then retrieves the required information fromthe interposer specification. At step 370, the makefile interposer maystore the retrieved information in a buffer for possible future use. Atstep 374, the command is interposed with the appropriate information forthe target platform. Once the command has been interposed, the commandis executed at step 378. The make utility then checks if the end of themakefile has been reached at step 382. If there are still more commandsto run, the process then loops back to step 358. If there are no morecommands to run, then process ends at step 386.

FIG. 3C is a flow diagram of an interposing process 300 according to athird embodiment. The process starts at step 304 where the makefileinterposer may first open and read the makefile. It reads one command atstep 308. Then at step 312, the makefile interposer may check theinterposer specification and an environment variable that indicateswhich platform the program is intended to run on. The makefileinterposer then retrieves the required information from the interposerspecification. At step 316, the command is interposed with theappropriate information for the target platform. Once the command hasbeen interposed, the command is executed at step 320. The interposerthen checks if the end of the makefile has been reached at step 324. Ifthere are still more commands to run, the process then loops back tostep 308. If there are no more commands to run, then process ends atstep 328.

FIG. 3D is a flow diagram of an interposing process 350 according to afourth embodiment. The process starts at step 354 where the makefileinterposer may first open and read the makefile. It reads one command atstep 358. Then at step 362, the makefile interposer may check to see ifthe information that needs to interposed has been previously accessedand buffered. If the information that needs to be interposed has beenbuffered, the process may move onto step 374. If the information has notbeen buffered, the process then proceeds to step 366 where the makefileinterposer may check the interposer specification and an environmentvariable that indicates which platform the program is intended to runon. The makefile interposer then retrieves the required information fromthe interposer specification. At step 370, the makefile interposer maystore the retrieved information in a buffer for possible future use. Atstep 374, the command is interposed with the appropriate information forthe target platform. Once the command has been interposed, the commandis executed at step 378. The interposer then checks if the end of themakefile has been reached at step 382. If there are still more commandsto run, the process then loops back to step 358. If there are no morecommands to run, then process ends at step 386. In one embodiment, themakefile interposer may read each command in the makefile and interposeas it reads each command. In another embodiment, the make fileinterposer may read all of the commands in the makefile and theninterpose all of the commands after they have all been read.

Because hardware, software and operating systems are constantly beingchanged and update, new platforms are constantly created and olderplatforms are constantly modified. As a result the makefile interposermay also include an interposer specification. The interposerspecification may contain information or macros which the makefileinterposer may use when interposing commands in the makefile. Theinterposer specification may be updated as new platforms are added andolder platforms are modified, thereby allowing the same makefile to beused for new platforms and older platforms that have been updated.

In one embodiment, the makefile interposer may be integrated with anIDE. The makefile interposer may be used to provide informationregarding dependencies to the IDE which may be displayed to thedeveloper. For example, a particular set of modules may need to beprecompiled before the program may be built because the program usesthose modules. The makefile would normally take care of building themodules first and then building the program after. This information maynot be readily apparent within an IDE as generally only source code andclass or object hierarchies are displayed. The makefile interposer wouldidentify these dependencies to the IDE and the IDE may displays thesedependencies to the developer in a separate user interface.

FIG. 4 is a block diagram illustrating an example of one of thecomputing systems 110 which may use embodiments as illustrated in FIGS.1A-3D. The computing system 400 includes a processor 430 that is incommunication with a memory 440 and a network interface 450. The networkinterface 450 may receive signals according to wired technologiesincluding but not limited to Ethernet, telephone (e.g., POTS), and fiberoptic systems, and/or wireless technologies including but not limited acode division multiple access (CDMA or CDMA2000) communication system, aGSM/GPRS (General Packet Radio Service)/EDGE (enhanced data GSMenvironment) or an IEEE 802.11b system. The system 400 may also includeone or more of an output device 420 such as a visual display and a userinput device 410 such as a keypad, touch screen, or other suitabletactile input device.

Referring to FIG. 4, the computing system 400 is represented as a seriesof interrelated functional blocks that may represent functionsimplemented by, for example the processor 430, software, somecombination thereof, or in some other manner as taught herein. Forexample, the processor 430 may facilitate user input via the inputdevice 410.

FIG. 5A illustrates an example mobile device 500. The mobile device 500can be, for example, a handheld computer, a personal digital assistant,a cellular telephone, a network appliance, a camera, a smart phone, anenhanced general packet radio service (EGPRS) mobile phone, a networkbase station, a media player, a navigation device, an email device, agame console, or a combination of any two or more of these dataprocessing devices or other data processing devices.

In some implementations, the mobile device 500 includes atouch-sensitive display 502. The touch-sensitive display 502 can beimplemented with liquid crystal display (LCD) technology, light emittingpolymer display (LPD) technology, or some other display technology. Thetouch-sensitive display 502 can be sensitive to haptic and/or tactilecontact with a user.

In some implementations, the touch-sensitive display 502 may include amulti-touch-sensitive display 502. A multi-touch-sensitive display 502can, for example, process multiple simultaneous touch points, includingprocessing data related to the pressure, degree, and/or position of eachtouch point. Such processing facilitates gestures and interactions withmultiple fingers, chording, and other interactions. Othertouch-sensitive display technologies can also be used, e.g., a displayin which contact is made using a stylus or other pointing device. Someexamples of multi-touch-sensitive display technology are described inU.S. Pat. Nos. 6,323,846, 6,570,557, 6,677,932, and 6,888,536, each ofwhich is incorporated by reference herein in its entirety.

In some implementations, the mobile device 500 can display one or moregraphical user interfaces on the touch-sensitive display 502 forproviding the user access to various system objects and for conveyinginformation to the user. In some implementations, the graphical userinterface can include one or more display objects 504, 506. In theexample shown, the display objects 504, 506, are graphic representationsof system objects. Some examples of system objects include devicefunctions, applications, windows, files, alerts, events, or otheridentifiable system objects.

In some implementations, the mobile device 500 can implement multipledevice functionalities, such as a telephony device, as indicated by aPhone object 510; an e-mail device, as indicated by the Mail object 512;a map devices, as indicated by the Maps object 514; a Wi-Fi base stationdevice (not shown); and a network video transmission and display device,as indicated by the Web Video object 516. In some implementations,particular display objects 504, e.g., the Phone object 510, the Mailobject 512, the Maps object 514, and the Web Video object 516, can bedisplayed in a menu bar 518. In some implementations, devicefunctionalities can be accessed from a top-level graphical userinterface, such as the graphical user interface illustrated in FIG. 5A.Touching one of the objects 510, 512, 514, or 516 can, for example,invoke a corresponding functionality.

In some implementations, the mobile device 500 can implement a networkdistribution functionality. For example, the functionality can enablethe user to take the mobile device 500 and provide access to itsassociated network while traveling. In particular, the mobile device 500can extend Internet access (e.g., Wi-Fi) to other wireless devices inthe vicinity. For example, mobile device 500 can be configured as a basestation for one or more devices. As such, mobile device 500 can grant ordeny network access to other wireless devices.

In some implementations, upon invocation of a device functionality, thegraphical user interface of the mobile device 500 changes, or isaugmented or replaced with another user interface or user interfaceelements, to facilitate user access to particular functions associatedwith the corresponding device functionality. For example, in response toa user touching the Phone object 510, the graphical user interface ofthe touch-sensitive display 502 may present display objects related tovarious phone functions; likewise, touching of the Mail object 512 maycause the graphical user interface to present display objects related tovarious e-mail functions; touching the Maps object 514 may cause thegraphical user interface to present display objects related to variousmaps functions; and touching the Web Video object 516 may cause thegraphical user interface to present display objects related to variousweb video functions.

In some implementations, the top-level graphical user interfaceenvironment or state of FIG. 5A can be restored by pressing a button 520located near the bottom of the mobile device 500. In someimplementations, each corresponding device functionality may havecorresponding “home” display objects displayed on the touch-sensitivedisplay 502, and the graphical user interface environment of FIG. 5A canbe restored by pressing the “home” display object.

In some implementations, the top-level graphical user interface caninclude additional display objects 506, such as a short messagingservice (SMS) object 530, a Calendar object 532, a Photos object 534, aCamera object 536, a Calculator object 538, a Stocks object 540, aAddress Book object 542, a Media object 544, a Web object 546, a Videoobject 548, a Settings object 550, and a Notes object (not shown).Touching the SMS display object 530 can, for example, invoke an SMSmessaging environment and supporting functionality; likewise, eachselection of a display object 532, 534, 536, 538, 540, 542, 544, 546,548, and 550 can invoke a corresponding object environment andfunctionality.

Additional and/or different display objects can also be displayed in thegraphical user interface of FIG. 5A. For example, if the device 500 isfunctioning as a base station for other devices, one or more“connection” objects may appear in the graphical user interface toindicate the connection. In some implementations, the display objects506 can be configured by a user, e.g., a user may specify which displayobjects 506 are displayed, and/or may download additional applicationsor other software that provides other functionalities and correspondingdisplay objects.

In some implementations, the mobile device 500 can include one or moreinput/output (I/O) devices and/or sensor devices. For example, a speaker560 and a microphone 562 can be included to facilitate voice-enabledfunctionalities, such as phone and voice mail functions. In someimplementations, an up/down button 584 for volume control of the speaker560 and the microphone 562 can be included. The mobile device 500 canalso include an on/off button 582 for a ring indicator of incoming phonecalls. In some implementations, a loud speaker 564 can be included tofacilitate hands-free voice functionalities, such as speaker phonefunctions. An audio jack 566 can also be included for use of headphonesand/or a microphone.

In some implementations, a proximity sensor 568 can be included tofacilitate the detection of the user positioning the mobile device 500proximate to the user's ear and, in response, to disengage thetouch-sensitive display 502 to prevent accidental function invocations.In some implementations, the touch-sensitive display 502 can be turnedoff to conserve additional power when the mobile device 500 is proximateto the user's ear.

Other sensors can also be used. For example, in some implementations, anambient light sensor 570 can be utilized to facilitate adjusting thebrightness of the touch-sensitive display 502. In some implementations,an accelerometer 572 can be utilized to detect movement of the mobiledevice 500, as indicated by the directional arrow 574. Accordingly,display objects and/or media can be presented according to a detectedorientation, e.g., portrait or landscape. In some implementations, themobile device 500 may include circuitry and sensors for supporting alocation determining capability, such as that provided by the globalpositioning system (GPS) or other positioning systems (e.g., systemsusing Wi-Fi access points, television signals, cellular grids, UniformResource Locators (URLs)). In some implementations, a positioning system(e.g., a GPS receiver) can be integrated into the mobile device 500 orprovided as a separate device that can be coupled to the mobile device500 through an interface (e.g., port device 590) to provide access tolocation-based services.

In some implementations, a port device 590, e.g., a Universal Serial Bus(USB) port, or a docking port, or some other wired port connection, canbe included. The port device 590 can, for example, be utilized toestablish a wired connection to other computing devices, such as othercommunication devices 500, network access devices, a personal computer,a printer, a display screen, or other processing devices capable ofreceiving and/or transmitting data. In some implementations, the portdevice 590 allows the mobile device 500 to synchronize with a hostdevice using one or more protocols, such as, for example, the TCP/IP,HTTP, UDP and any other known protocol.

The mobile device 500 can also include a camera lens and sensor 580. Insome implementations, the camera lens and sensor 580 can be located onthe back surface of the mobile device 500. The camera can capture stillimages and/or video.

The mobile device 500 can also include one or more wirelesscommunication subsystems, such as an 802.11b/g communication device 586,and/or a Bluetooth™ communication device 588. Other communicationprotocols can also be supported, including other 802.x communicationprotocols (e.g., WiMax, Wi-Fi, 3G), code division multiple access(CDMA), global system for mobile communications (GSM), Enhanced Data GSMEnvironment (EDGE), etc.

FIG. 5B illustrates another example of configurable top-level graphicaluser interface of device 500. The device 500 can be configured todisplay a different set of display objects.

In some implementations, each of one or more system objects of device500 has a set of system object attributes associated with it; and one ofthe attributes determines whether a display object for the system objectwill be rendered in the top-level graphical user interface. Thisattribute can be set by the system automatically, or by a user throughcertain programs or system functionalities as described below. FIG. 5Bshows an example of how the Notes object 552 (not shown in FIG. 5A) isadded to and the Web Video object 516 is removed from the top graphicaluser interface of device 500 (e.g. such as when the attributes of theNotes system object and the Web Video system object are modified).

FIG. 6 is a block diagram 600 of an example implementation of a mobiledevice (e.g., mobile device 500). The mobile device can include a memoryinterface 602, one or more data processors, image processors and/orcentral processing units 604, and a peripherals interface 606. Thememory interface 602, the one or more processors 604 and/or theperipherals interface 606 can be separate components or can beintegrated in one or more integrated circuits. The various components inthe mobile device can be coupled by one or more communication buses orsignal lines.

Sensors, devices, and subsystems can be coupled to the peripheralsinterface 606 to facilitate multiple functionalities. For example, amotion sensor 610, a light sensor 612, and a proximity sensor 614 can becoupled to the peripherals interface 606 to facilitate the orientation,lighting, and proximity functions described with respect to FIG. 5A.Other sensors 616 can also be connected to the peripherals interface606, such as a positioning system (e.g., GPS receiver), a temperaturesensor, a biometric sensor, or other sensing device, to facilitaterelated functionalities.

A camera subsystem 620 and an optical sensor 622, e.g., a chargedcoupled device (CCD) or a complementary metal-oxide semiconductor (CMOS)optical sensor, can be utilized to facilitate camera functions, such asrecording photographs and video clips.

Communication functions can be facilitated through one or more wirelesscommunication subsystems 624, which can include radio frequencyreceivers and transmitters and/or optical (e.g., infrared) receivers andtransmitters. The specific design and implementation of thecommunication subsystem 624 can depend on the communication network(s)over which the mobile device is intended to operate. For example, amobile device can include communication subsystems 624 designed tooperate over a GSM network, a GPRS network, an EDGE network, a Wi-Fi orWiMax network, and a Bluetooth™ network. In particular, the wirelesscommunication subsystems 624 may include hosting protocols such that themobile device may be configured as a base station for other wirelessdevices.

An audio subsystem 626 can be coupled to a speaker 628 and a microphone66 to facilitate voice-enabled functions, such as voice recognition,voice replication, digital recording, and telephony functions.

The I/O subsystem 640 can include a touch screen controller 642 and/orother input controller(s) 644. The touch-screen controller 642 can becoupled to a touch screen 646. The touch screen 646 and touch screencontroller 642 can, for example, detect contact and movement or breakthereof using any of a plurality of touch sensitivity technologies,including but not limited to capacitive, resistive, infrared, andsurface acoustic wave technologies, as well as other proximity sensorarrays or other elements for determining one or more points of contactwith the touch screen 646.

The other input controller(s) 644 can be coupled to other input/controldevices 648, such as one or more buttons, rocker switches, thumb-wheel,infrared port, USB port, and/or a pointer device such as a stylus. Theone or more buttons (not shown) can include an up/down button for volumecontrol of the speaker 628 and/or the microphone 66.

In one implementation, a pressing of the button for a first duration maydisengage a lock of the touch screen 646; and a pressing of the buttonfor a second duration that is longer than the first duration may turnpower to the mobile device on or off. The user may be able to customizea functionality of one or more of the buttons. The touch screen 646 can,for example, also be used to implement virtual or soft buttons and/or akeyboard.

In some implementations, the mobile device can present recorded audioand/or video files, such as MP3, AAC, and MPEG files. In someimplementations, the mobile device can include the functionality of anMP3 player, such as an iPod™. The mobile device may, therefore, includea 32-pin connector that is compatible with the iPod™. Other input/outputand control devices can also be used.

The memory interface 602 can be coupled to memory 650. The memory 650can include high-speed random access memory and/or non-volatile memory,such as one or more magnetic disk storage devices, one or more opticalstorage devices, and/or flash memory (e.g., NAND, NOR). The memory 650can store an operating system 652, such as Darwin, RTXC, LINUX, UNIX, OSX, WINDOWS, or an embedded operating system such as VxWorks. Theoperating system 652 may include instructions for handling basic systemservices and for performing hardware dependent tasks. In someimplementations, the operating system 652 can be a kernel (e.g., UNIXkernel).

The memory 650 may also store communication instructions 654 tofacilitate communicating with one or more additional devices, one ormore computers and/or one or more servers. The memory 650 may includegraphical user interface instructions 656 to facilitate graphic userinterface processing; sensor processing instructions 658 to facilitatesensor-related processing and functions; phone instructions 660 tofacilitate phone-related processes and functions; electronic messaginginstructions 662 to facilitate electronic-messaging related processesand functions; web browsing instructions 664 to facilitate webbrowsing-related processes and functions; media processing instructions666 to facilitate media processing-related processes and functions;GPS/Navigation instructions 668 to facilitate GPS and navigation-relatedprocesses and instructions; camera instructions 670 to facilitatecamera-related processes and functions; and/or other softwareinstructions 672 to facilitate other processes and functions, e.g.,access control management functions. The memory 650 may also store othersoftware instructions (not shown), such as web video instructions tofacilitate web video-related processes and functions; and/or webshopping instructions to facilitate web shopping-related processes andfunctions. In some implementations, the media processing instructions666 are divided into audio processing instructions and video processinginstructions to facilitate audio processing-related processes andfunctions and video processing-related processes and functions,respectively. An activation record and International Mobile EquipmentIdentity (IMEI) 674 or similar hardware identifier can also be stored inmemory 650.

The above detailed description of certain embodiments presents variousdescriptions of specific embodiments. However, the invention can beembodied in a multitude of different ways as defined and covered by theclaims. In this description, reference is made to the drawings whereinlike parts are designated with like numerals throughout.

The terminology used in the description presented herein is not intendedto be interpreted in any limited or restrictive manner, simply becauseit is being utilized in conjunction with a detailed description ofcertain specific embodiments. Furthermore, embodiments may includeseveral novel features, no single one of which is solely responsible forits desirable attributes or which is essential to practicing theinventions herein described.

The system may include various modules, tools, and applications asdiscussed in detail below. As can be appreciated by one of ordinaryskill in the art, each of the modules may include various sub-routines,procedures, definitional statements and macros. Each of the modules aretypically separately compiled and linked into a single executableprogram. Therefore, the following description of each of the modules isused for convenience to describe the functionality of the preferredsystem. Thus, the processes that are undergone by each of the modulesmay be arbitrarily redistributed to one of the other modules, combinedtogether in a single module, or made available in, for example, ashareable dynamic link library.

The system modules, tools, and applications may be written in anyprogramming language such as, for example, C, C++, BASIC, Visual Basic,Pascal, Ada, Java, HTML, XML, or FORTRAN, and executed on an operatingsystem, such as variants of Windows, Macintosh, UNIX, Linux, VxWorks, orother operating system. C, C++, BASIC, Visual Basic, Pascal, Ada, Java,HTML, XML and FORTRAN are industry standard programming languages forwhich many commercial compilers can be used to create executable code.

The above-described method may be realized in a program format to bestored on a computer readable recording medium that includes any kindsof recording devices for storing computer readable data, for example, aCD-ROM, a DVD, a magnetic tape, memory card, and a disk, and may also berealized in a carrier wave format (e.g., Internet transmission orBluetooth transmission).

While specific blocks, sections, devices, functions and modules may havebeen set forth above, a skilled technologist may realize that there aremany ways to partition the system, and that there are many parts,components, modules or functions that may be substituted for thoselisted above.

While the above detailed description has shown, described, and pointedout the fundamental novel features as applied to various embodiments, itmay be understood that various omissions and substitutions and changesin the form and details of the system illustrated may be made by thoseskilled in the art, without departing from the intent of the invention.

1. Within an integrated development environment, a method comprising:detecting building of a program within the integrated developmentenvironment, wherein the building includes a call to a file; dynamicallyintercepting the call with an interposer within the integrateddevelopment environment; directing the call to one or more replacementfiles; and completing building the program using the replacement files.2. The method of claim 1 wherein detecting building of a program withinthe integrated development environment comprises: detecting a “make”utility access to a descriptor associated with the program; anddetermining whether the descriptor references the file.
 3. The method ofclaim 1 wherein the file comprises a system library.
 4. The method ofclaim 1 wherein dynamically intercepting the call with an interposerwithin the integrated development environment comprises: determining ifthe call is directed to a platform-specific file; determining, with theinterposer, whether the call to the platform-specific file correspondsto a target platform; causing the call to be redirected if the call tothe platform-specific file does not correspond to the target platform.5. The method of claim 1 wherein directing the call to one or morereplacement files comprises modifying a descriptor associated with amake utility invoked to build the application, wherein the modificationcomprises modifying a path used to call the one or more replacementfiles.
 6. An apparatus having an integrated development environment, theapparatus comprising: means for detecting building of a program withinthe integrated development environment, wherein the building includes acall to a file; means for dynamically intercepting the call with aninterposer within the integrated development environment; means fordirecting the call to one or more replacement files; and means forcompleting building the program using the replacement files.
 7. Theapparatus of claim 6 wherein the means for detecting building of aprogram within the integrated development environment comprises: meansfor detecting a “make” utility access to a descriptor associated withthe program; and means for determining whether the descriptor referencesthe file.
 8. The apparatus of claim 6 wherein the means for dynamicallyintercepting the call with an interposer within the integrateddevelopment environment comprises: means for determining if the call isdirected to a platform-specific file; means for determining whether thecall to the platform-specific file corresponds to a target platform;means for causing the call to be redirected if the call to theplatform-specific file does not correspond to the target platform. 9.The apparatus of claim 6 wherein the means for directing the call to oneor more replacement files comprises means for modifying a descriptorassociated with a make utility invoked to build the application, whereinthe modification comprises modifying a path used to call the one or morereplacement files.
 10. An article of manufacture comprising acomputer-readable medium having stored thereon instructions that, whenexecuted, cause one or more processors to provide, within an integrateddevelopment environment, functionality to: detect building of a programwithin the integrated development environment, wherein the buildingincludes a call to a file; dynamically intercept the call with aninterposer within the integrated development environment; direct thecall to one or more replacement files; and complete building the programusing the replacement files.
 11. The article of claim 10 wherein theinstructions that cause the one or more processors to detect building ofa program within the integrated development environment compriseinstructions that, when executed, cause the one or more processors to:detect a “make” utility access to a descriptor associated with theprogram; and determine whether the descriptor references the file. 12.The article of claim 10 wherein the file comprises a system library. 13.The article of claim 10 wherein the instructions that cause the one ormore processors to dynamically intercept the call with an interposerwithin the integrated development environment comprise instructionsthat, when executed, cause the one or more processors to: determine ifthe call is directed to a platform-specific file; determine, with theinterposer, whether the call to the platform-specific file correspondsto a target platform; cause the call to be redirected if the call to theplatform-specific file does not correspond to the target platform. 14.The article of claim 10 wherein the instructions that cause the one ormore processors to direct the call to one or more replacement filescomprises instructions that, when executed, cause the one or moreprocessors to modify a descriptor associated with a make utility invokedto build the application, wherein the modification comprises modifying apath used to call the one or more replacement files.
 15. An apparatuscomprising: a makefile utility to build an application utilizing atleast a descriptor list associated with the application, the makefileutility to make calls to files included in the descriptor list to buildthe application; an interposer communicatively coupled with the makefileutility to monitor calls to files and to intercept calls to one or moreselected files, the interposer to modify the calls to the one or moreselected files to cause the calls to be directed to one or morereplacement files; a compiler communicatively coupled with the makefileutility and with the interposer to build the application utilizing theone or more replacement files.
 16. The apparatus of claim 15 wherein atleast one of the one or more selected files comprises a system libraryfile and at least one of the one or more replacement files comprises areplacement system library file.
 17. The apparatus of claim 16 whereinthe system library file is specific to a first computing platform andthe replacement system library file is specific to a second computingplatform.
 18. The apparatus of claim 15 further comprising an interposerspecification file to indicate to the interposer the selected files andthe replacement files.
 19. The apparatus of claim 18 further comprisingan environment variable specification to indicate to the interposer atype of target computing platform.